Intelligent part numbering system and method

ABSTRACT

A database design and associated support tools for storing Intelligent Part Numbering System (IPNS) metadata for the purpose of interfacing with information systems in a more efficient way, thereby reducing maintenance requirement and improving information technology (IT) searching options. Embodiments of the present invention are directed to a method, system, and computer-readable medium for storing one or more attributes of a part number family in a database as metadata. The method includes associating a part number code with each attribute in the database; receiving one or more user inputs, each user input indicating a selection of one of the attributes; determining the part number codes associated with each of the selected attributes; and generating a part number based on the part number codes associated with each of the selected attributes.

The present application is a continuation of U.S. patent applicationSer. No. 16/506,061, filed on Jul. 9, 2019, which is a continuation ofU.S. patent application Ser. No. 14/836,674, filed on Aug. 26, 2015,which claims benefit of provisional U.S. Patent Application No.62/043,304, filed on Aug. 28, 2014. The subject matter disclosed in allof the above applications is incorporated by reference in the presentapplication.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to database design and moreparticularly to a database design and associated support tools forgenerating and storing part numbers using metadata.

BACKGROUND OF THE INVENTION

Part numbering systems are used to uniquely identify a specific instanceof a product or good. Families of goods, which are sometimes called aseries, have some common attributes (series-based attributes) and someunique attributes that can be varied. A family of goods can be describedby listing, in lists or tables on a family/series specification sheet,each attribute options for the family of goods. Such attributes andassociated options may include attributes (e.g., size, color, andstyle), and the associated options (e.g. small, medium, or large; red,white, or blue; long, short, or mid). The owner of the family/serieswill assign a code to each option and define a specific order in whichthese codes are concatenated along with a predefined set of characterprefixes and suffixes to uniquely identify all the attributes of anindividual item. This unique identifier within a product family isreferenced by many names including, but not limited to, Item Number,Part Number, Stock Keeping Unit (SKU), Catalog Number, Part ID, and thelike. This method can be decoded at point of use by persons who arefamiliar with the family owner's specification practices. In the priorart, parts catalogs would typically include the codes for each option ina family or series. A purchaser, such as an engineer or technician,would try to identify the family/series of the part needed for aparticular project in the catalog, and then construct a part number fromthe option codes listed for the family/series of the part. This partnumber would then be used to order the part from the distributer ormanufacturer.

Prior art information systems are disconnected from this method of partnumbering systems because the information systems require a uniquecharacter string or part numbers which are indexed in a database withthe whole part number as an indexed key or part of a compound index.Prior art information systems store linked information (attributes) backto a single instance of a part number. This is in part due to the factthat enterprise resource planning (ERP) systems require a uniquecharacter string part number for each part number. ERP systems are usedby businesses to collect, store, manage and interpret data from manybusiness activities such as product planning, cost and development;manufacturing or service delivery; marketing and sales; inventorymanagement; and shipping and payment. ERP provides an integrated view ofcore business processes, often in real-time, using common databasesmaintained by a database management system. A part numbering systemneeds to be able to provide a part number than can be automaticallyrecognized by an ERP system.

When a purchaser uses a prior art information system, such as an onlineparts website, to find and order a part, the information system searchesthrough the entire database of indexed part numbers to find matchingpart numbers. Because of all of the possible combinations of options fora series of parts, there can be millions of possible part numberinstances (in some cases billions or even trillions). As a result,online parts distributors typically only include 5% to 10% of thepossible part number instances in their online database, for example, byincluding top selling items only. For an engineer or purchaser who needsa specialty part, the part number may not be available from thedistributor's information system. In addition, offering a new partseries for sale can involve several weeks of coding and data entry tomake the new part series available to customers via the distributor'sexisting online information system, representing a significant cost tothe distributor.

What is needed in the art is a database design and associated tools thatallow information systems to store and maintain product family/seriesinformation in metadata form without the hierarchical and full indexedlist of part numbers. Such a system would allow for rapid storage andretrieval of attributes and co-dependent attributes for a part numberthat may or may not be pre-loaded into an information system.

SUMMARY OF THE INVENTION

Embodiments of the present invention are directed to a method, system,and computer-readable medium for storing one or more attributes of apart number family in a database as metadata. The method includesassociating a part number code with each attribute in the database;receiving one or more user inputs, each user input indicating aselection of one of the attributes; determining the part number codesassociated with each of the selected attributes; and generating a partnumber based on the part number codes associated with each of theselected attributes.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the invention that follows may be better understood.Additional features and advantages of the invention will be describedhereinafter. It should be appreciated by those skilled in the art thatthe conception and specific embodiments disclosed may be readilyutilized as a basis for modifying or designing other structures forcarrying out the same purposes of the present invention. It should alsobe realized by those skilled in the art that such equivalentconstructions do not depart from the spirit and scope of the inventionas set forth in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more thorough understanding of the present invention, andadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 shows a block diagram is shown of computer system 100 suitablefor storing and/or executing a computer program product in accordancewith embodiments of the present invention;

FIG. 2 is the data extracted from a family specification data sheetshowing the various options available in an exemplary family or seriesof a part;

FIG. 3 is a flowchart showing a method for an intelligent part numberingsystem in accordance with embodiments of the present invention; and

FIG. 4 shows an exemplary user interface for embodiments of the presentinvention.

FIG. 5 shows an exemplary intelligent part numbering system databaseschema in accordance with embodiments of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The database design and associated tools in accordance with embodimentsof the present invention enable information systems to store andmaintain product family information in metadata form without ahierarchical and full indexed list of part numbers. Embodiments of thepresent invention enables rapid storage and retrieval of attributes andco-dependent attributes for a part number that may or may not bepre-loaded into an information system. The commercial benefits include areduction in storage and maintenance requirements for their use orcommercial promotion of a family of products. Embodiments of the presentinvention are built to work with existing IT systems and provideenhancement capability to existing IT solutions. Embodiments of thepresent invention have no limits to the number of attributes that can beconcatenated, the options that can be associated with an attribute, theseries that can be stored, the series owners that can be stored, and theproduct groups that can be represented.

FIG. 1 shows a block diagram is shown of computer system 100 suitablefor storing and/or executing a computer program product in accordancewith embodiments of the present invention. Computer system 100 includesat least one processor 102 coupled directly or indirectly to memoryelements through system bus 112. The memory elements comprise atangible, non-transitory, computer-readable medium and can include localmemory 106 employed during the actual execution of the program code,bulk storage 110, and cache memories 104 and 108 which provide temporarystorage of at least some program code in order to reduce the number oftimes code must be retrieved from bulk storage 110 during execution.Bulk storage 110, while shown as part of computer system 100, can alsoinclude remote bulk storage, also known as cloud storage, which providesremote storage accessible via network adapter 122 and network 124.Input/output or I/O devices (including but not limited to keyboards 120,displays 118, pointing devices 116, etc.) can be coupled to the systemeither directly or through intervening I/O controllers 114. Networkadapters 122 may also be coupled to computer system 100 to enable thesystem to become coupled to remote computer system 126 or remoteprinters or storage devices through intervening private or publicnetworks 124. Modems, cable modems, Ethernet cards, and wireless networkadapters (e.g., WiFi, Bluetooth, cellular) are just a few exemplarytypes of network adapters. Persons of ordinary skill in the art wouldunderstand that computer system 100 can be embodied in a variety of wayswithin the scope of the present invention including, but not limited to,a microcomputer, a smartphone, a tablet computer, a file server, amainframe computer system, or a partition on a virtual server in a cloudcomputing context.

FIG. 2 is the data extracted from a family specification data sheetshowing the various options available in an exemplary family or seriesof a part. The manufacturer (Mfg) of the part is Amphenol (AMPH). Theseries of the part is D38999. Each series can include series attributes,part number (PN) defining attributes (Part Number Sections), andcodependent attributes. Series attributes are attributes that are sharedamong all parts in the series.

Part number defining attributes (Part Number Sections) are attributesthat define a specific instance of a part according to the options thatare available for a series of parts. For a particular part numberinstance, only one value can be selected for part number definingattribute. As shown in the example of FIG. 2 , one part number definingattribute is shell style. The shell style options that are available foran instance of a part are: wall mount receptacle, jam nut receptacle,straight cable plug, box mount hermetics, and jam nut hermetics. Each ofthese shell style options is associated with a part number code that isused to define the part number having a particular shell style. The wallmount receptacle shell style has the part number code 20, the jam nutreceptacle shell style has the part number code 24, the straight cableplug shell style has the part number code 26, and so on. An instance ofthe series D38999 part having a wall mount receptacle shell style willinclude 20 in the position of the part number that corresponds to shellstyle option, giving a part number D38999/20. An instance of the seriesD38999 part having a jam nut receptacle shell style will include 24 inthe position of the part number that corresponds to shell style option,giving a part number D38999/24. An instance of the series D38999 parthaving a straight cable plug shell style will include 26 in the positionof the part number that corresponds to shell style option, giving a partnumber D38999/26.

Codependent attributes are attributes that depend on the selection of apart number defining attribute. Some codependent attributes require theselection of a particular part number defining attribute. Somecodependent attributes are unavailable for a part instance based uponthe selection of a particular part number defining attribute. Forexample, Product Life Cycle is an attribute that is dependent on whatContact Style option is selected. The “P-Pins” contact style has aproduct life cycle of 500 mates. The “S-Sockets” contact style has aproduct life cycle of 500 mates. The “H-Pins (1500)” contact style has aproduct life cycle of 1500 mates. The “J-Sockets” contact style has aproduct life cycle of 1500 mates. The end user does not specificallyselect an option code for a codependent attribute. The end user'schoices or part number attributes does dictate the codependent attributevalue. Another example would be fuel efficiency in miles per gallon(MPG) for automobile selections. Users select the Engine Type/Style (4Cylinder, 6 Cylinder, 8 Cylinder, Eco . . . Turbo). Each Engine Optionhas a codependent MPG Attribute that is associated with the selection ofthe primary attribute that is part of the Part Numbering System. Priorart information systems require a unique character string or partnumbers which are indexed in a database with that whole part number asan indexed key or part of a compound index. Prior art informationsystems store attributes back to a single instance of a part number.

FIG. 3 is a flowchart showing a method for an intelligent part numberingsystem in accordance with embodiments of the present invention. Themethod is a computer-implemented method preferably embodied in acomputer system such as exemplary computer system 100. The method ispreferably embodied as computer-executable instructions encoded on anon-transitory, computer-readable medium, such as local memory 106 orbulk storage 110. The computer-executable instructions, when executed byprocessor 103, cause computer system 100 to perform the following steps.

The method begins at step 302. At step 304, attributes of a part numberare stored in a database, such as database 130. Database 130 can be anydatabase known in the art for storing data, including but not limited tostructured query language (SQL) or Microsoft Access. The attributes arestored as metadata. That is, the attributes stored in the databasedescribe the data comprising part numbers for a series of parts.

At step 304, each attribute stored in step 302 is associated with a partnumber code. The part number code is a symbol or text string that can beused to identify the attribute in a part number. Information regardingthe position of the part number code in a part number is preferablyassociated with the attribute. The data can be entered manually by auser or imported automatically from an existing data store. For example,using the example shown in FIG. 2 , shell style is part number definingattribute associated with part number series D38999. One option for theattribute is the wall mount receptacle shell style. The wall mountreceptacle style is associated with part number code 20. In addition,the shell style part codes comprise the two digits following the seriescode. This information is also recorded in database 130.

At step 308, computer system 100 receives one or more user inputs, eachuser input indicating a selection of one of the attributes. The userinput can be received from a customer or purchaser. The user input canbe received from an owner or distributor of the parts who is taking anorder from a customer or purchaser. In a preferred embodiment, computersystem 100 receives the user input from remote computer system 126 vianetwork 124, for example, in a hypertext transfer protocol (http)transaction over the World Wide Web (www). In this way, a customer,engineer, or purchaser can select attributes of a part number series ina familiar manner using a web browser application, such as MicrosoftInternet Explorer, Google Chrome, Mozilla Firebox, Apple Safari, or thelike.

At step 310, computer system 100 determines the part number codesassociated with each of the selected attributes. Computer system 100looks up the selected attributes in database 130 and identifies the partnumber codes associated with each of the selected attributes. Forexample, if the user input indicates a selection of wall mountreceptacle for the shell style, then the computer system will determinefrom the metadata in the database 130 that the wall mount receptacleshell style has a part number code of 20. The computer can alsodetermine product availability based on attribute selection. Thecomputer can also determine which part number section options are validand invalid based on a set of rules.

At step 312, computer system 100 generates a part number based on thepart number codes associated with each of the selected attributes. Usingthe part number codes determined in step 310 and the informationregarding the positions of the part number codes within the part number,computer system 100 generates a part number for the instance of the parthaving the attributes selected by the user. For example, computer system100 receives user inputs indicating the following attribute selectionsfor a part in series D38999: wall mount receptacle shell style (partnumber code 20), anodized aluminum finish (part number code C), 3×20layout (part number code A98), pins contact (part number code P), andnormal rotation (part number code N). Computer system 100, using themetadata stored in database 130, generates the following part number:D38999/20CA98PN. The generated part number can be transmitted to theuser, preferably by being displayed to the user. The generated partnumber can be automatically entered into an electronic commerce systemso the user can place an order. The generated part number can beautomatically entered into an ERP system upon entry of the order so thatfullfillment of the order can commence. The method stops at step 314.

FIG. 4 shows an exemplary user interface for embodiments of the presentinvention. The user interface shown in FIG. 4 can be implemented as aweb page viewable in a web browser application using in a well-knownmethods. The user navigates to the web page displaying the partconfigurator for the part series in which the user is interested. In theexample of FIG. 4 , the user has navigated to the part configurator forthe Amphenol D38999 series of parts. The attributes are shown in tabularform as user-selectable cells. In the example shown in FIG. 4 , the userhas selected the wall mount receptable shell style having part numbercode 20. The selection is indicated by the square outline around thecell for the wall mount receptable shell style attribute. The partnumber is generated substantially in real-time as the user makesattribute selections. The “My Part Number” field shows the part numbercode for the wall mount receptacle properly appended to the part numberas D38999/20. As part number defining attributes are selected,codependent attributes are made available or unavailable for selectionbased upon whether the codependent attributes are compatible with theselected part number defining attributes. In a preferred embodiment, theuser can select or hover over the part number with pointing device 116and a pop up window will display descriptions of the selected attributesand any attributes that are inherited from the part series.

FIG. 5 shows an exemplary intelligent part numbering system databaseschema in accordance with embodiments of the present invention. Theinformation to the left of the dashed line is a schema of an existingdatabase for tracking items in a warehouse. The information of the rightof the dashed line is the schema for the database of the intelligentpart numbering system. The intelligent part numbering system can importinformation available in an existing warehouse inventory database anduse that information to dynamically generate part numbers based onselections made by a user. The data file structured on the right side ofthe dashed line in FIG. 5 is a normalized database design for anintelligent part numbering system in accordance with a preferredembodiment of the present invention. Storing the information thatdescribes a part number in many inter-related tables is a more efficientmethod. This normalized storage method reduces redundancy of datastorage. This method of storing data reduces the ongoing maintenancecosts. This method of data storage improves the integrity ofinformation. The complexity of data extraction of attributes surroundinga given part number is increased as compared to a flat file structure,however the benefits are justified. The data file structure on the leftside of the dashed line is for reference only and represents a typicalERP system.

Deployment tools include CRUD (CReate, Update, Delete) Maintenance,Series Import/Export Routines, Series Template Generators, Series PN andMetadata Expansion, Product Selector Character based, Product SelectorWEB Based Widget/App, Series Stock Status list by attribute combination.

Installing the IPNS Schema linking it to an existing ERP expands the ERPand extended systems (WEB sites and others) to work with seriesinformation from the metadata with or without having all uniqueconfigurations of a series loaded into the ERP's traditional 1 PN=1database entry in an “Item” file.

Exemplary code suitable for implementing this system includes thefollowing:

1) General Data Entry Functions: A set of maintenance programs thatworks with multiple temporary tables storing the metadata that describesa series that uses an intelligent part numbering system (IPNS) touniquely identify configurable options.

2) Export Function: A function called from the general data entryfunction that write IPNS metadata about a series generates from a set oftemporary tables to a common file format that can be open and used inmost spreadsheet applications, such as the .csv file format. When openin a spreadsheet the file has the look and feel of a human readablespecification data sheet.

3) Import Function: A function called from the general data entry thatreads a .csv or similar file format from a predefined data set formatand loads data into a set of temporary tables that define a seriesmetadata.

4) Build IPNS Schema Function: A function called from the general dataentry function that builds metadata with generated indexed identifiersto each component of the metadata. This function occurring in a singletransaction block to ensure data integrity for the identifying codes.

5) Expand IPNS Items Function: A function called from the general dataentry that walks down each available option for each section and createsearch index records for some or all possible configurations within aseries. This code is a recursive script that evaluates multipleheuristics including a logical flag for Expand (Yes/No) for each option,and a predefined set of rules for options that are invalid based onother options.

Although the present invention and its advantages have been described indetail, it should be understood that various changes, substitutions andalterations can be made herein without departing from the spirit andscope of the invention as defined by the appended claims. Moreover, thescope of the present application is not intended to be limited to theparticular embodiments of the process, machine, manufacture, compositionof matter, means, methods and steps described in the specification. Asone of ordinary skill in the art will readily appreciate from thedisclosure of the present invention, processes, machines, manufacture,compositions of matter, means, methods, or steps, presently existing orlater to be developed that perform substantially the same function orachieve substantially the same result as the corresponding embodimentsdescribed herein may be utilized according to the present invention.Accordingly, the appended claims are intended to include within theirscope such processes, machines, manufacture, compositions of matter,means, methods, or steps.

We claim as follows:
 1. A method of storing and retrieving data relatedto part numbers in a computer memory, the method comprising: configuringthe computer memory according to a database, the database includingmetadata organized according to a schema including: a manufacturerseries file for storing information about one or more product series,the manufacturer series file including: a series identification fieldfor storing a series identification code for each of the one or moreproduct series; a section count field for storing a section count numberfor each of the one or more product series, the section count numberindicating the number attributes associated with the product seriesidentified by the series identification code; a series attribute filefor storing information about each attribute in product series, theseries attribute file being a child file to the manufacturer seriesfile, the series attribute file including: an attribute identificationfield for storing an attribute identification code for each of theattributes associated with the product series; an attribute name fieldfor storing a description of the attribute being referenced by theattribute identification code; a part number sections file for storingpart number section information, the part number sections file being achild file to the series attribute file, the part number sections fileincluding: a section identification field for storing a sectionidentification code for each of the part number sections; an attributeidentification field for storing the attribute identification codeassociated with each of the section identification codes; a sectionposition field for storing a location of the each of the part numbersections within a final part number; storing one or more attributes of apart number family in the database according to the metadata schema;receiving one or more user inputs, each user input indicating aselection of one of the attributes; determining a part number codeassociated with each of the selected attributes; and generating a partnumber based on the part number codes associated with each of theselected attributes selected by the user.
 2. The method of claim 1 inwhich a part number code is inherited from the part number family. 3.The method of claim 1 in which attributes displayed to a user disappearbased on prior selections made by the user.
 4. The method of claim 1 inwhich the generated part number is automatically entered into anenterprise resource planning (ERP) system.
 5. The method of claim 4 inwhich automatically entering the generated part number into theenterprise resource planning (ERP) system causes a part to bemanufactured, the part having attributes defined by the generated partnumber.
 6. The method of claim 1 is which generating the part numbercauses a part to be manufactured, the part having attributes defined bythe generated part number.
 7. The method of claim 1, further comprisingconfiguring the computer memory according to a database, the databaseincluding metadata organized according to a schema including: a sectionoptions file for storing attribute value options, the section optionsfile being a child file to the part number sections file, the sectionoptions file including: an option identification field for storingoption identification codes associated with each of the attribute valueoptions; an attribute value field for storing attribute valuesindicating a value associated with each of the attribute value options;an option code field for storing option codes, the option codes beingassociated with each of the attribute value options; a series itemsection options file, the series item section options file being anindex file having two long integer fields comprising: an itemidentification field for storing one or more item identificationnumbers; an option identification field for storing the optionidentification code associated with each item identification number; andwherein the attribute value options of an item are encoded in the optionidentification code associated with each item identification number. 8.An intelligent part number data storage and retrieval system comprising:a computer processor; and a computer memory coupled to the computerprocessor, the computer memory encoded with computer-readableinstructions that, when executed by the computer processor, cause thesystem to perform any of the steps of: configuring the computer memoryaccording to a database, the database including metadata organizedaccording to a schema including: a manufacturer series file for storinginformation about one or more product series, the manufacturer seriesfile including: a series identification field for storing a seriesidentification code for each of the one or more product series; asection count field for storing a section count number for each of theone or more product series, the section count number indicating thenumber attributes associated with the product series identified by theseries identification code; a series attribute file for storinginformation about each attribute in product series, the series attributefile being a child file to the manufacturer series file, the seriesattribute file including: an attribute identification field for storingan attribute identification code for each of the attributes associatedwith the product series; an attribute name field for storing adescription of the attribute being referenced by the attributeidentification code; a part number sections file for storing part numbersection information, the part number sections file being a child file tothe series attribute file, the part number sections file including: asection identification field for storing a section identification codefor each of the part number sections; an attribute identification fieldfor storing the attribute identification code associated with each ofthe section identification codes; a section position field for storing alocation of the each of the part number sections within a final partnumber; storing one or more attributes of a part number family in thedatabase according to the metadata schema; receiving one or more userinputs, each user input indicating a selection of one of the attributes;determining a part number code associated with each of the selectedattributes; and generating a part number based on the part number codesassociated with each of the selected attributes.
 9. The system of claim8 in which a part number code is inherited from the part number family.10. The system of claim 8 in which attributes displayed to a userdisappear based on prior selections made by the user.
 11. The system ofclaim 8 in which the generated part number is automatically entered intoan enterprise resource planning (ERP) system.
 12. The system of claim 11in which automatically entering the generated part number into theenterprise resource planning (ERP) system causes a part to bemanufactured, the part having attributes defined by the generated partnumber.
 13. The system of claim 8 is which generating the part numbercauses a part to be manufactured, the part having attributes defined bythe generated part number.
 14. The data storage and retrieval system ofclaim 8, further comprising configuring the computer memory according toa database, the database including metadata organized according to aschema including: a section options file for storing attribute valueoptions, the section options file being a child file to the part numbersections file, the section options file including: an optionidentification field for storing option identification codes associatedwith each of the attribute value options; an attribute value field forstoring attribute values indicating a value associated with each of theattribute value options; an option code field for storing option codes,the option codes being associated with each of the attribute valueoptions; a series item section options file, the series item sectionoptions file being an index file having two long integer fieldscomprising: an item identification field for storing one or more itemidentification numbers; an option identification field for storing theoption identification code associated with each item identificationnumber; and wherein the attribute value options of an item are encodedin the option identification code associated with each itemidentification number.
 15. A non-transitory, computer-readable mediumencoded with computer-readable instructions for an intelligent partnumbering system that, when executed by one or more computer processorsof a data storage and retrieval system, cause the data storage andretrieval system to perform the steps of: configuring the computermemory according to a database, the database including metadataorganized according to a schema including: a manufacturer series filefor storing information about one or more product series, themanufacturer series file including: a series identification field forstoring a series identification code for each of the one or more productseries; a section count field for storing a section count number foreach of the one or more product series, the section count numberindicating the number attributes associated with the product seriesidentified by the series identification code; a series attribute filefor storing information about each attribute in product series, theseries attribute file being a child file to the manufacturer seriesfile, the series attribute file including: an attribute identificationfield for storing an attribute identification code for each of theattributes associated with the product series; an attribute name fieldfor storing a description of the attribute being referenced by theattribute identification code; a part number sections file for storingpart number section information, the part number sections file being achild file to the series attribute file, the part number sections fileincluding: a section identification field for storing a sectionidentification code for each of the part number sections; an attributeidentification field for storing the attribute identification codeassociated with each of the section identification codes; a sectionposition field for storing a location of the each of the part numbersections within a final part number; storing one or more attributes of apart number family in the database according to the metadata schema;receiving one or more user inputs, each user input indicating aselection of one of the attributes; determining a part number codeassociated with each of the selected attributes; and generating a partnumber based on the part number codes associated with each of theselected attributes.
 16. The non-transitory, computer-readable medium ofclaim 15 in which a part number code is inherited from the part numberfamily.
 17. The non-transitory, computer-readable medium of claim 15 inwhich attributes displayed to a user disappear based on prior selectionsmade by the user.
 18. The non-transitory, computer-readable medium ofclaim 15 in which the generated part number is automatically enteredinto an enterprise resource planning (ERP) system.
 19. Thenon-transitory, computer-readable medium of claim 18 in whichautomatically entering the generated part number into the enterpriseresource planning (ERP) system causes a part to be manufactured, thepart having attributes defined by the generated part number.
 20. Thenon-transitory, computer-readable medium of claim 15 is which generatingthe part number causes a part to be manufactured, the part havingattributes defined by the generated part number.
 21. The non-transitory,computer-readable medium of claim 15 further comprising configuring thecomputer memory according to a database, the database including metadataorganized according to a schema including: a section options file forstoring attribute value options, the section options file being a childfile to the part number sections file, the section options fileincluding: an option identification field for storing optionidentification codes associated with each of the attribute valueoptions; an attribute value field for storing attribute valuesindicating a value associated with each of the attribute value options;an option code field for storing option codes, the option codes beingassociated with each of the attribute value options; a series itemsection options file, the series item section options file being anindex file having two long integer fields comprising: an itemidentification field for storing one or more item identificationnumbers; an option identification field for storing the optionidentification code associated with each item identification number; andwherein the attribute value options of an item are encoded in the optionidentification code associated with each item identification number.